Junior Developer Test Task SearchTry NotionDrag image to repositionJunior Developer Test Task Welcome to Scandiweb Junior Developer test assignment!Thank you for your interest and time!This assignment tests minimum skills and knowledge required to successfully kick start your career at Scandiweb.The test helps us to assess your level and it helps you to check whether your level is already good to join us as a Junior Developer.Just like in real work, we have prepared a test automation script to test your work, so you do not need to guess whether you did good or bad. Now you can submit it  to the test automation script (instruction will be provided below) and get your test revision in about 10 seconds!Please, follow the instructions to make your test compatible with the test automation script and make sure that you score all PASS before you submit it for human evaluation.The expected outcome of the testA web-app (accessible by an URL) containing two pages for:Product list pageAdding a product pageHave any questions? Please check out our Frequently Asked Questions page! Junior Developer FAQ - frequently asked questionsCurious on what happens to your submitted test? Have a sneak peak!General coding requirementsThese are the listed mandatory technical requirements:Utilize OOP principles to handle differences in type logic/behaviorProcedural PHP code is allowed exclusively to initialize your PHP classes. Rest logic should be placed within class methods.For OOP you would need to demonstrate code structuring in meaningful classes that extend each other, so we would like to see an abstract class for the main product logic. Please take a look at the polymorphism provision.Also, MySQL logic should be handled by objects with properties instead of direct column values. Please use setters and getters for achieving this and don't forget to use them for both save and display logic.Meet PSR standards (https://www.php-fig.org)Avoid using conditional statements for handling differences in product typesThis means you should avoid any if-else and switch-case statements which are used to handle any difference between products.Do not use different endpoints for different products types. There should be 1 general endpoint for product savingPHP: ^7.0, plain classes, no frameworks, OOP approachjQuery: optionaljQuery-UI: prohibitedBootstrap: optionalSASS: advantageMySQL: ^5.6 obligatoryNOTE:React and vue.js is a huge advantage if you decide to use them for the frontend part, but not a requirement1. Product ListThis is the first page of the website, so should be accessible by <your_website>/Open full size imagePlease note, that on product list page product should not be split by product types - they should be sorted by primary key in database.MUST HAVE for the list items:SKU (unique for each product)NamePrice in $One of the product-specific attributes and its valueSize (in MB) for DVD-discWeight (in Kg) for BookDimensions (HxWxL) for FurnitureRequired UI elements:“ADD” button, which would lead to the “Product Add” page“MASS DELETE” action, implemented as checkboxes next to each product (should have a class: .delete-checkbox) and a button “MASS DELETE” triggering delete action for the selected products.There should be no pagination for the listing, all items should be on the same pageDo not show any notification messages or alert windows loading the list or after submitting ADD new product dialogueDefault viewFilterSortUntitledElementClassTextMass Delete buttonN (none)MASS DELETEDelete Checkbox.delete-checkboxNAdd Product ButtonNADDCount3Don't know what ID and Classes are? Please, read the following articles to understand them better! - ID - Classes2. Adding a product pageThis page should open once button "ADD" is pressed, and should be accessible by: <your_website>/add-productOpen full size imageThe page should display a form with id: #product_form, with the following fields:SKU (id: #sku)Name (id: #name)Price (id: #price)Product type switcher (id: #productType) with following options:DVD (can be value or text)Book (can be value or text)Furniture (can be value or text)Product type-specific attributeSize input field (in MB) for DVD-disc should have an ID: #sizeWeight input field (in Kg) for Book should have an ID: #weightEach from Dimensions input fields (HxWxL) for Furniture should have an appropriate ID:Height - #heightWidth - #widthLength - #lengthDefault viewFilterSortUntitledElementIDTextProduct form#product_formN (none)SKU input field#skuNName input field#nameNPrice input field#priceNType switcher#productTypeNDVD option in typesNDVDBook option in typesNBookFurniture option in typesNFurnitureDVD size input field#sizeNBook weight input field#weightNFurniture height field#heightNFurniture width field#widthNFurniture length field#lenghtNSave buttonNSaveCancel buttonNCancelCount15Add product page requirements:The form should be dynamically changed when the type is switchedSpecial attributes should have a description, related to their type, e.g.: “Please, provide dimensions” / “Please, provide weight” / “Please, provide size” when related product type is selectedAll fields are mandatory for submission, missing values should trigger notification “Please, submit required data”Implement input field value validation, invalid data must trigger notification “Please, provide the data of indicated type”Notification messages should appear on the same page without reloadingThe page must have a “Save” button to save the product. Once saved, return to the “Product List” page with the new product added.The page must have a “Cancel” button to cancel adding the product action. Once canceled, returned to the “Product List” page with no new products added.No additional dialogues like “Are you sure you want to Save / Cancel?”Finished? Now - time to AutoTest your work!As already mentioned at the beginning of the task, AutoTesting with the result of "PASSED" is a requirement before submitting the task to HRs!This software helps you to understand what you might be missing in your assignment to us. It also helps you to check if all core elements of the assignment are working properly.JustGo to AutoQATest your work!If failed, please make the necessary adjustments to make it PASSED!Once passed, please submit your test assignment to the HRs!How to submit?Share the code as a Bitbucket repository that is shared with a user with welcome@scandiweb.com email or you can keep it public as well.Send the URL via email to your recruiter, where the above two pages “Product List” and “Add Product” will be available without a password and ready to be used, adding also the link to the Bitbucket repository.Make sure the URL with this app is available 24/7 and is not dependent on your computer being “on” and connected. Only external deployment.You can use your preferred or this free PHP and MySQL hosting: https://www.000webhost.com/.3. Add to the email a screenshot of PASSED AutoQA!Good Luck! Well, we just looked up some random image in Unsplash for "good luck" and here it is, the Chinese dragon!(and that's our HR team celebration of a new hire)-Default view